feat(cursor): add token cost report with Cursor-metered total by EClinick · Pull Request #1745 · steipete/CodexBar

EClinick · 2026-06-24T21:41:31Z

Owner decision — product/privacy hold

Decision requested: Should CodexBar fetch detailed Cursor usage-event history through the existing cookie-authenticated dashboard session to calculate per-day/per-model cost estimates, or should Cursor remain limited to its summary usage/status data?

Tradeoff: The report makes otherwise hidden API-rate and Cursor-metered totals useful in the app and CLI. It also expands an authenticated dashboard integration into detailed event-history collection, depends on a private endpoint contract, and presents estimates that users may read as billing truth.

Recommendation: Do not land the current behavior yet. Prefer an explicit opt-in plus approved privacy/source wording before enabling this network-backed history fetch. If the owner accepts the existing-auth/no-new-setting model, the implementation below is prepared and exact-head CI is the remaining mechanical gate.

This PR is intentionally held for that owner decision; green CI does not make it merge-ready.

Summary

Adds a Cursor token-cost report to CodexBar, sourced from Cursor's cookie-authenticated dashboard API and reusing the existing Cursor session resolution (the same auth path as the status probe). Each usage event carries both a vendor list-price token cost (tokenUsage.totalCents) and the amount Cursor's plan actually deducts (chargedCents), so a single fetch yields both an API-rate per-day/per-model breakdown and a "Cursor-metered" window total covering the exact same window.

Core

CursorUsageEventsFetcher: pages POST /api/dashboard/get-filtered-usage-events, dedupes events on their natural key, and shapes them into a CostUsageDailyReport (API-rate) plus a metered window total (sum of chargedCents). Lenient numeric decoding handles Cursor serializing some numbers as strings, and the CSRF-protected POST sends the required Origin header.
CursorStatusProbe: generalized resolveSession so status and cost share one session-resolution flow (manual cookie, cached cookie, browser cookies, stored session, Cursor.app fallback); added fetchCostReport on top of it.
CostUsageFetcher: macOS-only Cursor branch over a rolling historyDays window (like Codex/Claude), with the session line tied to the current local day.
Enabled the Cursor tokenCost capability and added a Cursor-specific cost-estimate hint.

CLI

codexbar cost --provider cursor, honoring --days (1…365).
Reuses the usage path's cookie-source policy: skips with a notice when Cursor cookies are Off, and forwards the Manual header so the dashboard request uses the configured session instead of auto-resolving a different one. Cursor cost is gated to macOS.
Text output adds a Cursor-metered: $X (window) line; JSON adds meteredCostUSD. The unsupported-provider error lists supported providers dynamically.

App (UI)

Menu cost card renders the Cursor-metered line alongside the API-rate estimate, the Cursor dashboard hint, and an inline windowed cost chart consistent with other providers.

Live proof — `codexbar cost --provider cursor`

$ codexbar cost --provider cursor
Cursor Cost (API-rate estimate)
Today: $101.24 · 108M tokens
Last 30 days: $465.85 · 367M tokens
Cursor-metered: $4.76 (last 30 days)
From Cursor's usage dashboard at vendor token rates; may differ from your invoice.

$ codexbar cost --provider cursor --format json   # compact slice
{
  "provider": "cursor",
  "source": "web",
  "currencyCode": "USD",
  "historyDays": 30,
  "sessionCostUSD": 101.58,
  "last30DaysCostUSD": 466.19,
  "meteredCostUSD": 4.76,
  "daily_sample": [
    {
      "date": "2026-06-24",
      "totalCost": 101.58,
      "totalTokens": 108852907,
      "modelsUsed": ["example-released-model"],
      "modelBreakdowns": [
        { "modelName": "example-released-model", "totalTokens": 108852907, "cost": 101.58 }
      ]
    }
  ]
}

source: "web" confirms the live dashboard fetch; the Cursor-metered total and the per-model breakdown are both present. (Real token counts/amounts, lightly trimmed.)

Tests

CursorUsageEventsFetcherTests: pagination/dedupe, metered-cents summing (including nil-vs-zero), per-day/per-model mapping, and current-local-day session selection.
CursorStatusProbeTests: cost-report path over the shared session resolution.

Commands run

swift build --product CodexBarCLI — clean.
swift test --filter CursorUsageEventsFetcherTests — 10/10 passing (full Xcode toolchain).
make start — full app build, sign, and launch clean.

Screenshots

Notes

Cost is fetched over the network from Cursor's dashboard API using existing cookie-based auth, consistent with other network-backed providers (e.g. Bedrock). No new dependencies.

Cursor previously surfaced only status/quota, not per-model token cost. Add a cost report sourced from Cursor's cookie-authenticated dashboard API, reusing the existing Cursor session resolution. Core: - CursorUsageEventsFetcher pages get-filtered-usage-events, dedupes, and shapes events into an API-rate per-day/per-model report plus a Cursor-metered window total (sum of chargedCents). One fetch backs both numbers so they always cover the same window. - CursorStatusProbe.resolveSession generalizes the auth path so status and cost share one session-resolution flow; fetchCostReport runs on it. - CostUsageFetcher gains a macOS-only Cursor branch and a fetchAllHistory option (all-time window plus "All time" label when set). - Enable Cursor tokenCost capability and add a Cursor cost-estimate hint. CLI: - codexbar cost --provider cursor with --days and a new --all flag. - Text adds a "Cursor-metered" window line; JSON adds meteredCostUSD. App: - Menu cost card shows the Cursor-metered line; Preferences gains a global "Fetch full Cursor cost history" toggle wired through the settings store and the UsageStore refresh scope. Tests: - CursorUsageEventsFetcher pagination/dedupe/metered-cents and daily report mapping; CursorStatusProbe cost-report path.

Copilot

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

clawsweeper · 2026-06-24T21:42:32Z

Codex review: needs real behavior proof before merge. Reviewed July 11, 2026, 3:04 PM ET / 19:04 UTC.

Summary
Adds Cursor token-cost reporting from authenticated dashboard usage events across the app, CLI/server, documentation, and focused tests.

Reproducibility: not applicable. This PR adds a new Cursor cost-reporting capability rather than correcting a defined broken behavior on current main.

Review metrics: 3 noteworthy metrics.

Changed surface: 24 files; +1,286 / -135. The feature spans authentication, networking, caching, shared models, native UI, CLI/server output, docs, and tests.
Remote data sources: 1 private POST endpoint added. The authenticated detailed event-history request is the central product/privacy and compatibility boundary.
Posted UI proof: 4 screenshots; 0 show Cursor-metered. The images demonstrate adjacent Cursor cost UI but not the exact new metered-total rendering.

Merge readiness
Overall: 🦐 gold shrimp
Proof: 🦐 gold shrimp
Patch quality: 🐚 platinum hermit
Result: blocked until stronger real behavior proof is added.

Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch.

Rank-up moves:

Post fresh redacted exact-head packaged-menu and CLI proof visibly showing the Cursor-metered line and final source wording.
[P1] After the owner chooses the consent contract, implement and document that exact behavior.

Proof guidance:

[P1] Needs stronger real behavior proof before merge: Copied live CLI output shows the new fields, but none of the four screenshots visibly demonstrates the final packaged menu's Cursor-metered line; add fresh redacted exact-head menu and CLI evidence, update the PR body to trigger review, or ask a maintainer to comment @clawsweeper re-review.

Risk before merge

[P1] Existing users with Cursor and the global cost summary already enabled could begin a materially broader account-wide remote history fetch after upgrade without a dedicated consent step.
[P1] The feature depends on a private Cursor dashboard endpoint and response contract that can change independently of CodexBar.
[P1] The posted screenshots do not prove the final user-visible Cursor-metered line on the exact PR head.

Maintainer options:

Add explicit consent before merge (recommended)
Introduce a dedicated Cursor dashboard-cost opt-in and prove both fresh-install and upgrade behavior before landing.
Accept the existing-setting contract
Intentionally treat the current global cost toggle as consent for account-wide Cursor history and own the private-endpoint compatibility risk.
Pause detailed Cursor cost
Keep Cursor limited to its current summary status data if the broader collection scope is not worth the consent and endpoint risk.

Next step before merge

[P1] The repository owner must decide the consent/privacy contract; after that decision, the contributor can make the bounded setting/docs adjustment and refresh exact-head proof.

Maintainer decision needed

Question: Should CodexBar fetch detailed Cursor usage-event history through the existing authenticated session, or require a separate explicit opt-in for this account-wide remote data source?
Rationale: The code is technically reviewable, but only the repository owner can define whether existing provider and global cost settings constitute adequate consent for the broader private-endpoint data scope.
Likely owner: steipete — He owns the relevant current-main paths and explicitly placed this exact product/privacy hold.
Options:
- Require explicit opt-in (recommended): Add a separate user-controlled setting with approved privacy and source wording before detailed Cursor event-history requests are allowed.
- Reuse existing cost consent: Declare the existing Cursor-enabled plus Show cost summary combination sufficient consent and document the account-wide private endpoint prominently.
- Retain summary-only Cursor: Do not ship detailed event-history cost reporting until a stable source or different product contract is available.

Security
Needs attention: The code shows no concrete credential disclosure, but expanding an existing authenticated session to detailed account-history collection requires explicit consent and privacy approval.

Review details

Best possible solution:

Add a dedicated Cursor dashboard-cost opt-in with clear account-wide/private-endpoint wording, preserve the existing cookie-source and account-isolation behavior, then provide fresh redacted packaged-menu and CLI proof from the exact head.

Do we have a high-confidence way to reproduce the issue?

Not applicable: this PR adds a new Cursor cost-reporting capability rather than correcting a defined broken behavior on current main.

Is this the best way to solve the issue?

No, not in its current consent form; the shared fetch and session design is coherent, but a dedicated opt-in is the safer upgrade contract for account-wide authenticated history.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 0bb874930d6a.

Label changes

Label justifications:

P2: This is a substantial optional provider improvement with bounded impact rather than an urgent regression.
merge-risk: 🚨 compatibility: An upgrade could activate a new account-wide remote history fetch for users whose existing Cursor and cost-summary settings are already enabled.
merge-risk: 🚨 auth-provider: The patch expands cookie-authenticated Cursor session use to a private detailed usage-events endpoint and account-history data scope.
rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🦐 gold shrimp and patch quality is 🐚 platinum hermit.
status: 📣 needs proof: The PR needs real behavior proof before ClawSweeper can clear the contributor ask. Needs stronger real behavior proof before merge: Copied live CLI output shows the new fields, but none of the four screenshots visibly demonstrates the final packaged menu's Cursor-metered line; add fresh redacted exact-head menu and CLI evidence, update the PR body to trigger review, or ask a maintainer to comment @clawsweeper re-review.

Evidence reviewed

Security concerns:

[medium] Confirm consent for detailed authenticated history — docs/cursor.md:78
This expands Cursor cookie use from summary status checks to account-wide detailed usage-event collection through a private endpoint, so the owner must approve the data scope before merge.
Confidence: 0.99

What I checked:

Repository policy applied: The full AGENTS.md was read; provider isolation, cookie-import safety, focused validation, and fresh packaged-bundle UI proof materially informed the review. (AGENTS.md:1, 0bb874930d6a)
Feature remains necessary: Current main marks Cursor token-cost summaries unsupported, while the PR enables the capability and adds the dashboard event-history implementation. (Sources/CodexBarCore/Providers/Cursor/CursorProviderDescriptor.swift:30, 6343b1afc48b)
Authenticated request boundary: The exact head adds a bounded cookie-authenticated POST to Cursor's private usage-events endpoint, sets a matching Origin header, validates HTTP/auth failures, and aggregates detailed account events. (Sources/CodexBarCore/Providers/Cursor/CursorUsageEventsFetcher.swift:210, 6343b1afc48b)
Current consent behavior: The PR treats enabling the global cost summary while Cursor is enabled as opt-in to remote, account-wide dashboard history collection, which is the unresolved upgrade and privacy choice. (docs/cursor.md:77, 6343b1afc48b)
Owner decision remains open: The repository owner reviewed the implementation, called it substantially stronger, directly fixed the disabled-source contract, and explicitly held merge for the authenticated-dashboard product/privacy decision and final proof. (Sources/CodexBarCLI/CLICostCommand.swift:370, 43c87553e123)
Real behavior proof gap: All four posted GitHub screenshots were downloaded and inspected; they show Cursor API-rate costs, settings, and charts, but none visibly shows the new Cursor-metered line. (Sources/CodexBar/MenuCardView+Costs.swift:144, 6343b1afc48b)

Likely related people:

steipete: Current-main history connects him to Cursor session resolution and shared token-cost infrastructure; he also reviewed this feature, set the product/privacy hold, and committed the disabled-source contract fix. (role: feature owner and reviewer; confidence: high; commits: 7ddcf28b0442, 43c87553e123; files: Sources/CodexBarCore/Providers/Cursor/CursorStatusProbe.swift, Sources/CodexBarCore/CostUsageFetcher.swift, Sources/CodexBar/UsageStore+TokenCost.swift)

What the crustacean ranks mean

🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

How this review workflow works

ClawSweeper keeps one durable marker-backed review comment per issue or PR.
Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
Maintainers can also comment @clawsweeper review to request a fresh review only.
Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

Review history (5 earlier review cycles)

reviewed 2026-07-01T08:27:32.793Z sha 43c8755 :: needs real behavior proof before merge. :: [P1] Include Cursor auto session identity in cost scope | [P2] Document the remote Cursor cost contract
reviewed 2026-07-06T17:48:18.838Z sha 6bdb63a :: needs real behavior proof before merge. :: [P1] Scope Cursor auto cost cache to the resolved session | [P2] Document the remote Cursor cost contract
reviewed 2026-07-06T18:46:16.960Z sha 613342a :: needs real behavior proof before merge. :: none
reviewed 2026-07-11T02:55:55.784Z sha fb5c0b4 :: needs real behavior proof before merge. :: none
reviewed 2026-07-11T03:22:38.002Z sha 079da53 :: needs real behavior proof before merge. :: none

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 2209a9b639

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

… compiling Adding meteredLine to TokenUsageSection without a default made the synthesized memberwise initializer require it at every call site, breaking existing callers and tests that predate the Cursor-metered line. Add an explicit initializer that defaults meteredLine to nil so those call sites keep compiling.

The Cursor cost fetch always auto-resolved cookies, ignoring the cookie-source setting the status path respects. Thread a cursorCookieHeaderOverride from UsageStore through CostUsageFetcher into the Cursor cost report: forward the manual header when the source is Manual, skip the fetch entirely when it is Off, and fall back to auto resolution otherwise. Include the cookie source in the cost scope signature so toggling re-fetches.

…ping totalUsageEventsCount used a strict Int decode, so a string-encoded count (the API serializes some numbers as strings) became nil and could short-circuit pagination. Route it through the lenient CursorEventNumber decoder like every other numeric field. Also fix the paginate/dedupe test whose third event timestamp crossed into the next UTC day: it expected one day-entry while the correct grouping produced two. Move it onto the same UTC day so it exercises single-day grouping and dedup as intended.

EClinick · 2026-06-24T23:48:30Z

@clawsweeper re-review

clawsweeper · 2026-06-24T23:48:33Z

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

- Add Cursor to the inline cost-dashboard allowlist and key the Preferences cost-status line off supportsTokenCost so the Cursor card shows cost like Claude/Codex. - Drop the cursor-specific all-time history feature (the "Fetch full Cursor cost history" toggle, its settings plumbing, the CLI --all flag, the "All time" label, and the history-span sizing). Cursor now uses the shared "History window: N days" setting, so the inline chart draws legible windowed bars instead of the full account history. - Keep the Cursor-metered total, now scoped to the selected window.

EClinick · 2026-06-25T00:03:15Z

@openclaw-mantis visual task: verify CodexBar shows Cursor token cost with a Cursor-metered line and dashboard-source copy using redacted Cursor account data.

loadCursorTokenSnapshot now derives the session value from the current local day instead of the latest history entry, so a stale day is never labeled "Today" in the menu or CLI. This matches the Codex/Claude cost window behavior. Adds a focused test covering the stale-latest case.

tokenUsageHint had no Cursor case, so the shared menu/inline cost card fell back to the generic local-logs estimate copy for dashboard-derived Cursor data. Return the Cursor dashboard hint instead.

CLI `cost --provider cursor` now resolves the configured Cursor cookie source the same way the usage path does: it skips the fetch (with a notice) when cookies are Off and forwards the Manual header so the dashboard request uses the configured session instead of auto-resolving a different one. Also gates Cursor in costSupportedProviders to macOS, since supportsTokenSnapshot(.cursor) is macOS-only and the CLI otherwise advertised Cursor cost on platforms where it can only fail.

EClinick · 2026-06-25T00:32:25Z

@clawsweeper re-review

clawsweeper · 2026-06-25T00:32:27Z

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

EClinick · 2026-06-25T00:32:32Z

@codex review

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8632505417

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

EClinick · 2026-06-25T00:39:52Z

@clawsweeper re-review

EClinick · 2026-06-25T01:17:00Z

😎

EClinick · 2026-06-25T21:10:57Z

@steipete 🐐 how's this looking?

Resolve conflicts in two files by combining both intents: - InlineUsageDashboardContent: keep Cursor in the cost-history provider list and adopt main's more specific tokenCostInlineDashboardEnabled gate. - PreferencesGeneralPane: keep main's cost-summary display-style picker and padded VStack wrapper, and add the Cursor cost status line. Keep `make check` green after the merge: - DRY UsageStore.refreshTokenUsage via a resetTokenState(for:resetFetchMarkers:) helper so the body stays under the function_body_length limit. - Scope line_length disables to the Cursor usage-event JSON fixtures, matching the existing MistralUsageParserTests convention.

steipete · 2026-07-01T06:35:46Z

Maintainer review against current main (55327375) and exact head 02bcdede:

The data path is substantially stronger than the older cost proposals: it reuses Cursor auth resolution, paginates and deduplicates events, preserves local-day “Today” semantics, and keeps API-rate estimates separate from Cursor-metered totals. Focused tests are green: CursorUsageEventsFetcherTests (10), CursorStatusProbeTests (38), CostUsageTokenSnapshotDaySelectionTests (5), and CLICostTests (5).

I am holding the merge for the remaining product/auth decision and documentation gap. This adds an authenticated remote dashboard source to the app, CLI, and server, but docs/cursor.md and docs/cli.md still describe the old behavior. Please document the endpoint/auth fallback, the remote-vs-local meaning of the total, pagination/cache behavior, and codexbar cost output before landing. Refresh packaged menu/CLI proof after rebasing; avoid the generic provider/menu overlap in #1736.

Recommendation: approve as an opt-in Cursor dashboard cost source once the auth/privacy choice is explicit and docs/proof match the final UI. No merge from this review.

steipete · 2026-07-01T06:54:36Z

Maintainer follow-up: pushed 43c87553e to this branch.

The fix closes the concrete CLI/server contract gap found during review: when Cursor cost is requested while the Cursor cookie source is Off, codexbar cost --provider cursor now fails explicitly (including structured JSON output), and /cost returns a provider error row instead of silently omitting Cursor. Added regression coverage for the disabled-source payload.

Exact-head proof:

swift test --filter CLICostTests — 6 passed
swift test --filter CLIServeRouterTests — 41 passed
make check — passed, including SwiftFormat and strict SwiftLint
make test — all 44 shards passed
structured autoreview — clean, no accepted/actionable findings
GitGuardian Security Checks — passed on 43c87553e

Recommendation remains: keep this open rather than merge yet. The implementation is strong, but enabling authenticated Cursor dashboard access still needs the product/privacy decision, user-facing docs (docs/cursor.md and CLI docs), and coordination with #1736. Refresh packaged screenshots after that overlap lands and the final auth contract is selected.

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 43c87553e1

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

EClinick · 2026-07-06T19:59:26Z

@steipete sorry for late response, here ya go

# Conflicts: # Sources/CodexBarCLI/CLIServeCommand.swift # Sources/CodexBarCore/CostUsageFetcher.swift

# Conflicts: # Sources/CodexBar/PreferencesDisplayPane.swift # Sources/CodexBar/UsageStore.swift

# Conflicts: # Sources/CodexBar/PreferencesMenuPane.swift

Copilot AI review requested due to automatic review settings June 24, 2026 21:41

Copilot AI reviewed Jun 24, 2026

chatgpt-codex-connector Bot reviewed Jun 24, 2026

View reviewed changes

Comment thread Sources/CodexBar/MenuCardView.swift

Comment thread Sources/CodexBarCore/CostUsageFetcher.swift Outdated

style(cursor): wrap long Preferences subtitle to satisfy swiftformat

a3aaa75

EClinick added 3 commits June 24, 2026 15:19

clawsweeper Bot added proof: 📸 screenshot Contributor real behavior proof includes screenshot evidence. merge-risk: 🚨 compatibility 🚨 Merging this PR could break existing users, config, migrations, defaults, or upgrades. labels Jun 24, 2026

EClinick added 3 commits June 24, 2026 17:29

fix(cursor): show dashboard cost hint on the menu and inline cards

f92c3d6

tokenUsageHint had no Cursor case, so the shared menu/inline cost card fell back to the generic local-logs estimate copy for dashboard-derived Cursor data. Return the Cursor dashboard hint instead.

chatgpt-codex-connector Bot reviewed Jun 25, 2026

View reviewed changes

Comment thread Sources/CodexBarCore/CostUsageFetcher.swift Outdated

Comment thread Sources/CodexBar/UsageStore.swift Outdated

fix: report disabled Cursor cost source

43c8755

chatgpt-codex-connector Bot reviewed Jul 1, 2026

View reviewed changes

Comment thread Sources/CodexBar/UsageStore.swift Outdated

clawsweeper Bot added rating: 🦪 silver shellfish Thin PR readiness signal; proof, validation, or implementation needs work. and removed rating: 🦐 gold shrimp Decent PR readiness signal, but merge confidence is limited. labels Jul 1, 2026

EClinick added 3 commits July 6, 2026 10:43

Merge origin/main into feat/cursor-token-cost

6bdb63a

Include Cursor auto session identity in cost cache scope

718963b

docs: describe Cursor dashboard cost source and CLI output

613342a

clawsweeper Bot added rating: 🦐 gold shrimp Decent PR readiness signal, but merge confidence is limited. and removed rating: 🦪 silver shellfish Thin PR readiness signal; proof, validation, or implementation needs work. labels Jul 6, 2026

EClinick added 2 commits July 10, 2026 16:53

Merge remote-tracking branch 'origin/main' into feat/cursor-token-cost

fb5c0b4

# Conflicts: # Sources/CodexBarCLI/CLIServeCommand.swift # Sources/CodexBarCore/CostUsageFetcher.swift

Merge remote-tracking branch 'origin/main' into feat/cursor-token-cost

079da53

# Conflicts: # Sources/CodexBar/PreferencesDisplayPane.swift # Sources/CodexBar/UsageStore.swift

clawsweeper Bot removed the proof: 📸 screenshot Contributor real behavior proof includes screenshot evidence. label Jul 11, 2026

Merge remote-tracking branch 'origin/main' into feat/cursor-token-cost

6343b1a

# Conflicts: # Sources/CodexBar/PreferencesMenuPane.swift

Conversation

EClinick commented Jun 24, 2026 • edited by steipete Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Owner decision — product/privacy hold

Summary

Core

CLI

App (UI)

Live proof — codexbar cost --provider cursor

Tests

Commands run

Screenshots

Notes

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Uh oh!

clawsweeper Bot commented Jun 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

Uh oh!

EClinick commented Jun 24, 2026

Uh oh!

clawsweeper Bot commented Jun 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

EClinick commented Jun 25, 2026

Uh oh!

EClinick commented Jun 25, 2026

Uh oh!

clawsweeper Bot commented Jun 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

EClinick commented Jun 25, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

Uh oh!

EClinick commented Jun 25, 2026

Uh oh!

EClinick commented Jun 25, 2026

Uh oh!

EClinick commented Jun 25, 2026

Uh oh!

steipete commented Jul 1, 2026

Uh oh!

steipete commented Jul 1, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

EClinick commented Jul 6, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

EClinick commented Jun 24, 2026 •

edited by steipete

Loading

Live proof — `codexbar cost --provider cursor`

clawsweeper Bot commented Jun 24, 2026 •

edited

Loading

clawsweeper Bot commented Jun 24, 2026 •

edited

Loading

clawsweeper Bot commented Jun 25, 2026 •

edited

Loading